Published: 2006-02-19
Applies to: Content Studio all versions pre 5.2
Type: Information
Symptoms
When you update a document the document goes out of scope in the full text index and will not be found in a full-text query.
Cause
This problem occurs when there is an approved content that is changed. When a document is approved a new content is created and the old content is kept in the revision history. At this time the new content is not full-text indexed but the old one still is but since Content Studio only looks in the currently approved content the document appears to have disappeared. However after that the next full or incremental population of the full-text index has been performed the document appears again.
Resolution
An administrator can start an incremental population of the full-text index and this will solve the problem.
This problem has been fixed in Content Studio version 5.2
This problem has been fixed in Content Studio version 5.2
Status
This problem is by design. Content Studio uses the full-text engine of SQL Serve and SQL Server cannot detect and re index changed documents in the background if the changed field is of the text or image datatype.
Starting with version 5.2 Content Studio requires at least SQL Server 2005 and can use the new varbinary(max) which supports automatic background tracking for re-indexing.
Starting with version 5.2 Content Studio requires at least SQL Server 2005 and can use the new varbinary(max) which supports automatic background tracking for re-indexing.